Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference

Local Buffer Size (-l)

Use Local Buffer Size (-l) to change the size of the local record buffer in which Progress stores all variables, work files, and records that are in use at one time for a user.

Operating system and syntax	UNIX Windows	-l n
Use with	Maximum value	Minimum value	Single-user default	Multi-user default
Client Session	4,000,000,000	1	200	200

n

The size of the local record buffer in 1KB units.

The maximum size of the local record buffer is 4GB for most systems. If you get one of the following error messages, you need to increase the size of this buffer:

SYSTEM ERROR: bfget: No space. Increase -l parameter. SYSTEM ERROR: bfxpnd: No space. Increase -l parameter.

The Local Buffer Size (-l) limit is a soft limit; so if your application needs to exceed the limit, Progress automatically increases it and issues a WARNING message. The WARNING is written to the current output (if there is current output) and to the log file (LG).

You can force Progress to adhere to the specified -l limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress, issues the WARNING message when you exceed the Local Buffer Size limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note that -hardlimit also enforces the limits set by the Directory Size (-D), the Maximum Memory (-mmax), and the Nested Blocks (-nb) startup parameters, so the STOP condition is raised when any of the specified limits is reached.